第一次看此系列文的朋友，請先移步到 Day 1 – 如何開始？進行方式、自我介紹實戰 哦！

🎬 情境故事

今天你的團隊需要和另一個開發小組開會，討論一個共用 API 的改版。會議中要解釋目前的狀況、提出修改建議，還要確保對方了解時程與風險。

今日目標：學會在跨團隊會議中「清楚表達立場」與「確認共識」。

🤖 Config Prompt

[Config]
- Day: Day26 – Cross-team Meeting
- Scenario: You’re a backend engineer in a cross-team meeting with the frontend team, discussing a shared API update. You need to explain progress, mention a concern, and confirm next steps.

🎯 開始進行練習

記得把對話錄下來，自己聽一次，想想有哪裡不自然、哪裡需要調整。

📌 小技巧

可以參考以下結構來進行對話：

1. 合作的另一個團隊是誰（Frontend / QA / Infra / PM...）
2. 合作的目的或任務是什麼
3. 我的部分是什麼、目前狀況如何
4. 預期的時程、風險或依賴有哪些

🆘 今日救命句

• 救命句：
  Let’s make sure we’re on the same page.
• 爭取思考時間：
  Give me a second to think how to explain this.

🔑 核心句型

1. 說明目前狀況

   • We’re currently integrating your team’s API.
   • The implementation is halfway done on our side.

2. 提出問題或風險

   • One concern is the version compatibility.
   • We might face delays if the endpoint changes again.

3. 表示合作需求

   • We need your team’s confirmation before deployment.
   • Could you share your testing schedule?

4. 確認共識與行動

   • So, we’ll align on the new release date, right?
   • Does that sound reasonable to your team?

📝 Final Report

Per-turn Corrections
Turn 2: You said, "The API is about to create, cancel, and modify an order."
Rewrite: "You mean: The API is about creating, canceling, and modifying orders in the order book."
Alternative phrasing: "In other words, the API lets you create, cancel, or change orders."
Turn 5: You said, "I updated the document on JIRA and I'll share a link."
Rewrite: "You mean: I updated it on JIRA and I'll share the link."
Alternative phrasing: "In other words, I've put the update on JIRA and I'll give you the link."
Turn 7: You said, "I have small question for API timestamp format..."
Rewrite: "You mean: There's a small question about the API time format..."
Alternative phrasing: "In other words, I noticed a small issue with how we handle the time format."
Top 3 Patterns
Articles (a/the): Sometimes missing "a" or "the."
Rule: Just remember, a little "a" or "the" can help the sentence flow.
Prepositions: Small slips with prepositions like "for" and "on."
Mnemonic: Think "on JIRA" like "on a platform."
Word Order: Occasionally a slight word order tweak helps.
Tip: Keep the main idea up front and then add details.
Phrase Pack (5–7 ready-to-use lines)
"The API handles creating, canceling, and modifying orders."
"I'll update it on JIRA and share the link with you."
"We use a Unix timestamp so we don't have to worry about time zones."
"If everything's okay, you'll get a 200 response."
"If there's a parameter error, you'll see a 400."
"If the server has an issue, it'll return a 500 error."
Intonation Tip
Emphasize key numbers like "200," "400," and "500" a bit more clearly. For example: "You'll get a 200, or a 400, or a 500."
Fluency & Pronunciation Notes
Your clarity is good. Just keep sentences short and steady.
Great job repeating corrected sentences. That helps with fluency.
Pay a little attention to article use; you’re improving each time.
Overall, you’re doing really well with pronunciation and pacing.
Key Focus for Next Time
Practice a bit more with articles (“a,” “the”).
Keep working on short, clear word order.
A quick 2–3 minute drill: shadow a few corrected sentences or swap out words to build confidence.